docs(apparmor): add warning about profile persistence#23381
Conversation
✅ Deploy Preview for docsdocker ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
across reboots, as `/etc/apparmor.d/containers` will not be loaded, leading to the example `nginx` container not being able to start.
|
Thanks for the PR. We'd like to make our product docs better, but haven't been able to review all the suggestions. As our docs change often and quickly diverge, we do not have the bandwidth to review and rebase old PRs. If the updates are still relevant, please add a comment and review our contribution guidelines to rebase your PR against the latest version of the docs. This helps our maintainers focus on active contributions. If there's no activity, this PR will be closed in 30 days. To remove the stale label: Comment |
|
Closing this PR as there hasn't been any activity for a long time. If the updates are still relevant, please review our contribution guidelines and create a new PR against the latest version of our docs. |
across reboots, as
/etc/apparmor.d/containerswill not be loaded, leading to the examplenginxcontainer not being able to start.Description
Following the example to set up a custom apparmor profile.
I was suprised, that the profile suggested being located in
/etc/apparmor.d/containerswas not automatically loaded after a reboot.This is because apparmor only loads files directly located in
/etc/apparmor.d/*or known folder locations according to the Policy Layout.This led to my container not being able to start with error:
For this reason, I've added a warning section in the docs.
Reviews